home *** CD-ROM | disk | FTP | other *** search
- Path: interramp.com!usenet
- From: Barnett@interramp.com (Barnett E. Kurtz)
- Newsgroups: comp.lang.c++
- Subject: Re: HELP!!
- Date: Mon, 05 Feb 1996 22:19:58 GMT
- Organization: EntroData, Inc.
- Message-ID: <4f5vt3$jnk@usenet7.interramp.com>
- References: <4f4ln2$8ef@nntp.igs.net>
- Reply-To: Barnett@interramp.com
- NNTP-Posting-Host: ip118.philadelphia.pa.interramp.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- Dave,
-
- I believe the dlls need to reside in a directory that your executable
- can locate. The default search includes \windows\system, and most
- folks put copies of their debug/production owl/crt dlls there. Having
- them in \bcc45\bin is not enough. Borland includes a utility that
- allows you to swap debug/production builds on the fly. That's why they
- are there. See also 'distribution' in the docs.
-
- Please, next time post in comp.os.ms-windows.programmer, etc.
-
- Dave Hebert <daveh@ptbo.igs.net> wrote:
-
- >Okay, here's the deal.
-
- >I'm a very new C++ programmer. I'm in a Computers and Information
- >Systems course at a college in Peterborough, Ontario, Canada.
-
- >Here's my problem.
-
- >Recently I purchased turbo C++ v4.5 so I could do all my work at home as
- >computer time at the college is limited.
-
- >The first thing I did after I installed it was open a new project and
- >code:
-
- >#include <owl\applicat.h>
-
- >int OwlMain(int, char*[])
- >{
- > TApplication app("Tiniest App");
- > return app.Run();
- >}
-
- >I then proceeded to compile and run. It compiled then linked and then I
- >get three error messages:
-
- >"Can't find OWL250.DLL"
- >"Can't find BIDS45.DLL"
- >"Can't find BC450RTL.DLL"
-
- >That's bullshit because they ARE there!
-
- >What's the problem?
-
-
-
- -
- barnett@interramp.com
- -
-
-